Associating notifications of the status of a data network by use of a topology editor

ABSTRACT

A method for assigning an event to a device on a network is described by using a topology editor as user-controlled interface. The event is represented as a labeled graphic indication. Other devices on a data network, also represented graphically, are to be assigned to the event by using the user-controlled interface. A rule is then defined and associated with the event. When a condition, as defined by the rule is met by an application or device on the network, all of the devices assigned to the event are notified of the condition met by the rule in accordance with such graphically defined relationships.

FIELD OF INVENTION

The invention is related to the field of data networks, in particularthe communication of the status of devices on a data network.

BACKGROUND OF THE INVENTION

In the operation of a data network, devices linked through the networkcommunicate data back and forth to each other. Some of the datacommunicated represents a message representing the status of a device onthe network. The substance of such a message may indicate conditionssuch as a device may be inoperative, currently busy processing data, thedevice is free to receive new data, and the like. When communicated toother devices on the network, the devices receiving such a message maychange their operation in response to the message.

This type of communication of messages between devices on a networkrepresents a point-to-point communication system, where one message iseffectively broadcasted to all of the devices on a network. In the caseof a network having many devices, it is possible that a considerableamount of network bandwidth in consumed by the presence of statusmessages. Moreover, many of these status messages are not relevant for anumber of devices on the network. Hence, these devices have to commitresources to filtering such non-relevant messages while having networkbandwidth wasted due to the communication of such messages.

One approach for limiting the waste of bandwidth is to use a computerprogram such as a firewall that prohibits certain types of messages ordata from entering into a local network from an outside connection. Thedevices' that are connected through the local network are then sparedfrom having bandwidth consumed by non-relevant messages. Theconfiguration of a firewall or other filtering/monitoring programtypically requires a system administrator to manually configure avariety of rules for each device of a network. Therefore, a large amountof time is devoted to this manual configuration operation, whereby itbecomes difficult for a system administrator to modify the operation ofa system, without devoting a large amount of time to implement suchchanges.

SUMMARY OF THE INVENTION

A method for assigning an event pertaining to the operation of a deviceon a network by using a user controlled topology editor. The event isrepresented as a labeled graphic indication. Devices on a network, alsorepresented graphically, are assigned to the event by using theuser-controlled interface. A rule is then defined and associated withthe event. When a condition, as defined by the rule is met by the statusof an application or device on the network, all of the device elementsassigned to the event are notified of the condition met by the rule inaccordance with a messaging standard.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram of a data network in accordance with oneembodiment of the present invention;

FIG. 2 is a block diagram of an operation of a messaging system inaccordance with one embodiment of the present invention;

FIG. 3 is a representation of a graphic window for defining an eventassociated with a device on the data network;

FIG. 4 is a representation of a graphic window used for defining when anevent notification is issued to a device on the data network;

FIG. 5 is a flowchart illustrating a method of defining and implementinga rule associated with an event for a device on the data network;

FIG. 6 is a representation of a user interface used for selecting rulesand associated devices on the data network;

FIG. 7 is a representation of a user interface used for selecting aevent and devices associated with the selected rule; and

FIG. 8 is a representation of a user interface used for selecting asecond event and devices associated with the second selected rule.

It should be understood that the drawings are for purposes ofillustrating the concepts of the invention and are not necessarily theonly possible configuration for illustrating the invention.

DETAILED DESCRIPTION

The preferred embodiment of the invention operates in consideration ofthe Simple Network Management Protocol (SNMP) as defined in the RequestFor Comments 2571 (RFC 2571) entitled AN ARCHITECTURE FOR DESCRIBINGSNMP MANAGEMENT FRAMEWORK from April 1999. Although SNMP is described inthe detailed description, any messaging system for use on a data networkmay be used, using the principles of the present invention.Additionally, the description of the user interface is preferablyimplemented for use by a web browser as INTERNET EXPLORER or NETSCAPEusing a programming language as ACTIVEX or JAVA. Other forms ofprogramming languages or interfaces may be selected in accordance withthe principles of the present invention.

In reference to the operation of a SNMP standard, several terms arefrequently used. A SNMP managed device is a network device that containsan SNMP agent and resides on a data network. Managed devices collect andstore management information (such as disk errors, temperature, videoand audio status) and make this information available to other networkeddevices using the SNMP protocol.

An SNMP agent is a software module that resides in a SNMP manageddevice. An agent has local knowledge of management information andtranslates device or network status information into a form compatiblewith SNMP.

An SNMP manager is an application that monitors SNMP managed devices.One or more managers (also referred to as management stations) manyexist in a network and monitor any of the managed devices. An SNMPmanager may also be used to control devices and/or network functions anda SNMP manager can operate as a SNMP agent.

A management information base (MIB) is a collection of managed objects(variables) that are properties of a device and are organizedhierarchically. Each SNMP agent maintains it own the MIB. Additionally,MIBs are used as definition data for prescribing the relationship of adevice's operation to format of a SNMP transmitted command, by use of aSNMP manager.

An SNMP trap, as a notification (as a type of action provider), enablesan agent to notify a management station of significant events such aserrors on a network or a device. Traps may be sent unsolicited on thenetwork and will be received by management stations configured todisplay such traps for that device. Management stations also are able tocommunicate with other management stations by the use of traps.

Traps may be defined for different conditions or statuses pertaining todevices or a network. An informational trap indicates a change in thestate in a system that does not impact normal operation. Informationaltraps also provide general information about a device or network such asconfiguration information, system set up, software version, and thelike. A warning trap is a message that does not require immediate actionbut informs a user that some action may be necessary for systemoperation. For example, a warning trap indicates that a device on anetwork may soon run out of storage space. An alarm trap is a messagethat requires specific actions to be taken immediately. Both types oftraps may be used as action providers that are notifications concerninginformation or an alarm condition related to the operation of thenetwork.

A topology editor is a user-controlled interface that is used toestablish functional relationships between devices on a data network,although any type of network may be used. For example, a topology editoris used to designate that output from a selected computer is outputtedon a selected printer, this relationship is established through the useof graphic elements. Graphic elements represent icons, folders, or otherrepresentations that graphically indicate the function or status of adevice on a network and the relationships between such devices. Forinstance, a computer icon represents a computer (on the data network)and a folder containing several computer icons represents a specificworkgroup. Other uses of a topology editor and graphical elements are tobe appreciated, in accordance with the principles of the presentinvention.

FIG. 1 represents a diagram of a data network in accordance with oneembodiment of the present invention. Data network 100 is a networkedsystem of computers, servers, routers, and other devices thatcommunicate by the use of a computer protocol and transport system, asknown in the art. Preferably, data network 100 uses a Transport ControlProtocol/Internet Protocol (TCP/IP) as defined in RFC 791 entitledINTERNET PROTOCOL DARPA INTERNET PROGRAM PROTOCOL SPECIFICATION fromSeptember 1981, to communicate messages between devices. The SNMPmessages are communicated on top of the application layer of a TCP/IPprotocol stack, as known in the art. Alternatively, a User DatagramProtocol (UDP) transport layer as defined in RFC 768, entitled USER DATAPROTOCOL from August 1980, may be used for communicating traps ormessages to devices on data network 100. In an alternative embodiment ofthe present invention, an instant messaging standard may also be used.

Computers 10, 15, 20 and 25 represent computers that are networked toeach other through data network 100. Computers 10, 15, and 20, and 25are connected to the network through the use of a communicationinterface such as a network card, modem, wireless interface, or othermeans capable of communicating data over of network. Typically,computers are used for running applications such as e-mail, videorendering, internet browsing, and the like, where data is required to becommunicated over data network 100, in order for such programs to beoperational. Preferably, computers 10, 15, and 20 are controlled throughthe use of a web browser and/or user interface capable of activatingcomputer programs for monitoring the status of other devices on datanetwork 100.

Computer peripheral 25 is a device coupled to data network 100 for useby computers 10, 15, and 20. Computer peripheral 25 may be a device suchas a printer, data storage device, communication interface, CD-ROM, DVDplayer, display device, audio device, input interface, and the like.

Server 30, connected to data network 100, is used for obtaining computerdata files and other related information for operating programs oncomputers 10, 15, and 20. For example, an Internet application runningon computer 10 requires a data file from server 30. Once receivedthrough data network 100, the received data file is rendered on computer10. Additionally, server 30 may operate as a web cache that storesfrequently requested web pages and other data for use by computers 10,15 and 20.

Router 40, as part of data network 100, is used as a means forcommunicating Internet Protocol requests to other devices accessiblethrough network fabric 50, such as remote computer 60 and remote server70. Specifically, data network 100 for illustrative purposes isseparated into two different segments, local network 75 and remotenetwork 80. Communications between both network segments arecommunicated through network fabric 50. Router 40 optionally acts as afiltering mechanism (firewall) to screen data transmitted and receivedfrom devices comprising remote network 80. Such filtering operations areknown in the art. Additionally, router 40 may use a form of NetworkAddressable Translation (NAT) to further screen data from remote network80 that may corrupt the operation of devices of local network 75.

Remote computer 60 and remote server 70 form remote network 80. Theoperation of both of these components is similar to computers 10, 15,and 20 and server 30, as described above, except that remote computer 60and remote server 70 communicate to the devices forming local network 75through network fabric 50. Additionally, such communications transmittedby remote computer 60 or remote server 70 are optionally filtered byrouter 40, or by any other type of filtering program that is present oncomputers 10, 15, and 20.

FIG. 2 is a block diagram of an operation of a messaging system inaccordance with one embodiment of the present invention. In a preferredembodiment of the present invention, messaging system 200 operates inview of the SNMP messaging standard using of SNMP traps. The format ofan SNMP trap comprises a SNMP version number (referring to the versionof SNMP used), a community name (used for authenticating a SNMP trap),and SNMP Protocol Data Unit (PDU). The PDU is the message that forms thebasis the error messages sent between devices on a network. Sample PDUcommands and their function are shown in TABLE I. TABLE 1 PDU COMMANDSCOMMAND DESCRIPTION getrequest PDU command sent from SNMP manager to anagent to retrieve values of Object Identifiers (OID) representing eventsat the point at of the agent getnextrequest PDU command from SNMPmanager to an agent for obtaining the next set of OID values from anagent getresponse PDU command from an agent to a SNMP manager thatreturns the OID values requested in the getrequest command setrequestPDU command from SNMP manager to agent that sets up the valuesrepresenting an OID trap PDU command from agent to SNMP managernotifying the manager of an event

Messaging system 200 is managed via a SNMP manager operated by console205, preferably implemented as a user interface on a computer. Console205 is a control interface that manages the operation of devices on datanetwork 100 and the SNMP based messages communicated between suchdevices. In the present embodiment, console 205 controls operations suchas registering a system event corresponding to the operation of adevice, canceling an operation of a device, determining if thecancellation of an operation of a device has been activated, and theconfiguration of rules determining when selected devices are notifiedabout a system event, although other operations may be controlled byconsole 205.

Different system events or system operations are distinguished from eachother by having the SNMP manager (the functions represented by console205) assign different OIDs to each event. The definitions for suchevents are obtained by using a MIB corresponding to a device, or areference database that provides either a SNMP manager or agent theability to look up an OID as part of a received PDU command.

The registration of a system event, via console 205, is for thedefinition of the applications or functions of a device residing onnetwork 200. Such an operation would use a “setrequest” command with acorresponding OID as set up by an SNMP manager communicating with theappropriate SNMP agent. When communicated, the SNMP agent will returnback a “trap” message to the SNMP manager indicating that such anoperation has occurred. Alternatively, an SNMP manager may use a“setrequest” command to indicate to a device to proceed with or toterminate an operation.

In the present example, router 40 has an embedded web server thatrenders console 205 as a user interface that is accessed via a webbrowser and/or application capable of rendering HTML compatible code.Alternatively, console 205 is generated and controlled by a computerprogram accessible through the network such as action manager 215. Inthis embodiment, action manager 215 operates as an SNMP manager thatcontrols the flow of messages representing the set up and communicationof messages for a defined action provider (SNMP trap or notification).

A user operating computer 10 accesses the web server to enable andcancel the operation of different operations of devices on network 200,such communications are transmitted via SNMP, as explained above. Byusing console 205, a user enables (enables) a local Domain Name Server(DNS) application and virus filtering programming embedded within router240. Action manager 215 in response to the commands issued throughconsole 205 activates two SNMP messages that are transmitted to a SNMPagent that resides in router 40. One SNMP message corresponds to theactivation of the DNS application, the other SNMP message activates thevirus-filtering program. Other applications used as known in the art.

The assignment of both of the DNS and virus filtering application toserver 30 is illustrated in FIGS. 6, 7, and 8. Specifically, a usercontrolled interface 600 is shown, in FIG. 6, where the different systemapplications are represented as folders labeled as EVENT A, EVENT B, andEVENT C, such labels may be changed at will. Additionally, usercontrolled interface 600 contains graphic representations of devicesavailable through network 100 including computers 10, 15, and 20, server30, router 40, remote computer 60, and remote server 70. By using userinterface 600, a user establishes a connection between the graphicrepresentations of devices and the “RULES” displayed as folders.

When a user desires to associate a rule to a device, the user selects agraphic representation of a device, for example by clicking an iconrepresenting the device, and dragging such an icon into one of therendered folders. In the present example, EVENT A represents the DNSapplication and EVENT B represents the virus protection application. InFIG. 7, a user interface 700 is shown where a user associates the DNSapplication to router 40, by having the user select the graphicrepresentation of router 40 and dragging the representation over tofolder 710 representing EVENT A now labeled as DNS. Console 205 now willassociate any messages pertaining to the DNS application to router 40.

The assignment of an application to a device, by use of user interface700 may be done actively or passively. In an active state, the SNMPmanager controlled by user interface 700 (via action manager 215) sendsa SNMP setrequest command to the SNMP agent corresponding to router 40.This setrequest as to tells the agent module to send any messagesinvolving the DNS application to the SNMP manager as trap commands. Apassive state involves the SNMP manager listening for messages regardingthe DNS application, as broadcasted from the SNMP agent of router 40. Inthis case, the SNMP manager has not notified the SNMP agent tospecifically broadcast messages concerning the DNS application to theSNMP manager. Other implementations of SNMP messaging (or othermessaging systems) may be utilized, in accordance with the principles ofthe present invention.

Similarly in FIG. 8, a user interface 800 is shown where a userassociates (registers) a virus protection application to router 40 byhaving the user select a graphic representation of router 40, anddropping the representation in folder 810, denoted as EVENT B nowlabeled as VIRUS. It is to be appreciated that other devices of anetwork may be associated with other applications, in the mannerdescribed above.

Referring back to FIG. 2, console 205 is also used to configure rulesassociated with particular program or event. As shown in FIG. 6, afolder representing a particular program may also be used to associatean event with such a program. For example, the DNS application forserver 40 may be configured to transmit an event notification to certaindevices on the network when a requested domain name is unable to beresolved. The condition determining when such an event notification isissued, and to which devices, is configured by using the user interface700 of FIG. 7. In addition to router 40 being associated with folder710, computers 10 and 20, and remote computer 60 are associated withfolder 710 by using the registration approach described above.

This approach may be done where the SNMP manager program operated aspart of the action manager 215 informs router 40 to transmit SNMP trapmessages to all devices associated with folder 710. This is done byusing either a series of SNMP “setrequest” commands for each device tobe informed or a global “setrequest” command. Alternatively, the SNMPmanager may forward any received SNMP trap commands regarding theoperation of the DNS application to all of the devices associated withfolder 710. Additionally, SNMP messages issued as action providers bythe SNMP manager, may be used to control the operation of devices of thedata network. Other implementations of notifying devices may beselected, in accordance with the principles of the present invention.

Rules pertaining to a specific folder are configured by selectingoptions as presented in the example of FIG. 3. Specifically, when userselects folder 710, an actions entry window 300 (or menu) is generated,such a window is operated in as part of the user controlled interface.Event selection tab 305 provides a point of selection for a user toselect between different folders representing different system events.Rule window 320 allows a user to create or define the attributes forspecific rules defined for a specific event. In the present example, anew rule is added to rule window 320 by “right-clicking” any part of thearea defined by rule window 320. Properties of the new rule are definedby selecting the rule in rule window 320 and enabling properties button315. Correspondingly, the rules configured relate to the SNMP commandsthat set up the messages transmitted between SNMP agents and SNMPmanagers, as described above.

Examples of types of modifiable properties associated with a rule areshown as message severity option 325, message option 330, and actionoption 340. Message severity option 325 establishes the notificationpriority of an event when the conditions of a rule are met. In thepresent example, an alarm notification pertains to an event of a highpriority, a warning pertains to an event of a medium priority, and aninformation/reset pertains to an event associated with a low priority.

Message option 330 enables a user to select a class of message thattriggers a defined rule. For example, classes of messages include errormessages indicating an error in the operation an application, statusmessages indicating the status of a device, termination messagesindicating the completion of tasks, and other messages classes that maybe grouped based on the content of the messages. Similarly, messages mayalso be allocated assigned by subsystem, for instance all the messagespertaining to different classes of devices such servers, computers,peripheral devices and the like, or by type of application. When theSNMP manager receives a message of a particular class, the defined rulemay be triggered.

Action option 340 presents options controlling the rendering of eventnotifications as SNMP messages. Specifically, these instructions tell anSNMP agent or other SNMP manager how to render an event notification.Various options include a sound (beep), a visual alert, a text alert,and/or a combination thereof. Selected options for a specific event areconfirmed by activating OK button 350. The selected or modified rulespertaining to an event are then saved to repository 220 (see FIG. 2),after confirmation for the operation of the SNMP manager. Alternatively,other modalities may be selected for action option 340, such as e-mailto a remote device, a pager alert, or other notification modality to aremote device.

FIG. 4 is a representation of a graphic window used for defining optionsaffecting event notification issuance to a device on the data network,in accordance with an embodiment of the present invention. Manydifferent options may be implemented as to control how or when an eventnotification is rendered. In the current example, an ignore messageoption is shown, with ignore message window 400 representing a globaloption that allows a user to use a user interface to have messages (SNMPtraps) concerning a event be ignored by devices on the network. Theactivation of window 400 is enabled by a user selecting a folder (asshown in FIG. 6) and using a user controlled device to select an ignoremessage option.

Message window 400, provides an ignore all messages option 405, thatsquelches all of the messages related to a system event. The duration ofthe ignore operation may be set either as a permanent operation byselecting permanent selector 410 or temporarily by selecting temporaryselector 415 and defining a duration of time for this option to beactive. A user selects a starting and ending time for the activation ofthe temporary ignore option. The selected options are confirmed byactivating OK button 420. The selections are then saved to repository220 (see FIG. 2), after confirmation.

Referring back to FIG. 2, the options selected via console 205 controlsthe operation of action manager 215 that integrates the set up,communication, and routing of messages through a network. All of thecomponents that communicate with action manager 215 exist as part of acomputer program, application program interface (API), or other type ofcomponent capable of communicating messages over a network.Specifically, all of the options selected via console 205 are stored inrepository 220 by action manager 215. Repository 220 may be a storagedevice or other means capable of storing MIB and OID data and/or othertypes of definition data.

The operation of action manager 215 is conducted through the monitoringof system messages received through notification manager 210, which arepart of the workflow of a SNMP manager, for an illustrative embodimentof the present invention. Such messages are the system or statusmessages (SNMP traps) generated by devices on a network to indicate thedifferent types of operations. In the present example, router 40generates messages concerning the operation of a DNS application or avirus protection application that are transmitted to devices overnetwork 100. Preferably, router 40 specifically transmits a statusmessage about the operation of an application that is received andprocessed by notification manager 210. The format of such a message maybe a SNMP based message, e-mail, or any other type of messaging modalitycapable relaying a notification. Optionally, notification managermonitors traffic on network 100 specifically looking for data defined asstatus messages, as known in the art such as, and not limited to errorconditions of devices or the operational status of such devices.

Once a message is received, notification manager 210 forwards thesubstance of the message to action manager 215, such as InternetProtocol address of the message's origin, the application referred to inthe message, and the indicated status in the message. Action manager 215then compares the substance of the received message to the rulespertaining to the operation of an event by using MIB data or other datafor such definitions.

If the received status message matches conditions defined for one of therules, action manager 215 prepares an action notification associatedwith the matching rule. Specifically, the action notification will be astatus message as defined by the conditions of a matching rule. If theconditions of a rule are matched, action manager 215 communicates theaction notification to action provider 230 for dissemination to networkdevices, as defined by the event group related to the matching rule. Inan illustrative embodiment of the present invention, the SNMP managerinforms all SNMP agents associated with each device of an event group bythe use of a SNMP trap. Optionally, action manager 215 instructs actionprovider 230 how the action notification is to be rendered on a notifieddevice, such as an audible, visual, and/or text notification, asdescribed above.

FIG. 5 is a flowchart illustrating a method of defining and implementinga rule associated with an event for a device on a data network. Ruledefinition process 500 begins with the definition of an event pertainingto the operation of a network or devices on the network in step 510. Asdescribed above, the event is assigned a definition by use of a userinterface (as shown in FIGS. 6, 7, and 8) generated by console 205 andaction manager 215. The user interface renders the event as a graphicelement as a folder, icon or other type of graphic representation (step515). In the preferred case, the graphic element is also labeled withtext as to indicate the operation represented by the event. For example,in FIG. 7, folder 710 labeled as DNS represents an event relating to theoperation of a DNS server.

In step 520, the user interface is used to assign a device to aparticular event. In the preferred embodiment, a graphic representationof a device on a network is selected, by use of a mouse, and is draggedto a folder representing an event. Once the graphic representation of adevice is dropped into the folder, the selected device will be notifiedof any actions that are related to the event when a rule is activated.Step 525 allows a user to modify an event associated with a device byusing a user-controlled interface. This operation allows more devices tobe associated with an event, or attributes of the event (such as thelabel the event) can be modified, A rule is assigned to a selected eventin step 530. This is step is also enabled by a user operating a userinterface and creating a rule, as shown in FIG. 3. The options of therule may be modified in step 535 as accomplished by using the userinterface. When created or modified, the rule is preferably stored inrepository 220 as at least one condition that is activated wheninformation in a message (as received by notification manager 210)matches such a condition, as defined by definition data, OID or MIBdata.

A rule associated with an event is activated in step 540 upon thematching of a predefined condition or set of predefined conditions.Preferably, action manager 215 compares a received system message to aset of rules, as stored in repository 220. If the message matches theconditions for a particular rule, step 550 is activated where the deviceor devices associated with the event, as an event group, are transmittedan action notification in accordance with the conditions defined by theactivated rule. The notification is transmitted, as an SNMP trap, over adata network by action provider 230 for rendering on a device that isassociated with the event. Such a rendering operation is a visual,audible, and/or text message, performed either in accordance withinstructions in the notification or as default options at the site ofthe device rendering such a notification.

In an alternative embodiment of the present invention, a topology editoris used to define the relationships between different consumer devicescoupled through the use of a data network. For example, a set of HAVI (aconsumer device interoperability standard) enabled devices areconfigured to communicate with each other, through the use of the userinterface described above. Hence, a Personal Video Recorder (PVR) wouldbe capable of communicating with a television set if conditionsdescribing the operation of the PVR are met such as a warning about ashortage of storage space. The PVR communicates the warning message toother HAVI enabled devices. In this case, the topology editor definesthe type of messages to be rendered and how such messages should berendered on a receiving device. Hence, the television set renders thePVR warning message in accordance with the parameters defined by thetopology editor. Other examples of the use of a topology editor are tobe appreciated, in accordance with the principles of the presentinvention.

It is appreciated that other modalities may be used to translate andsystem messages. Having described preferred embodiments for SNMP basedmessaging system it is noted that modifications and variations can bemade by persons skilled in the art in light of the above teachings forother messaging modalities such as e-mail, SOAP, instant messaging, andthe like. It is therefore to be understood that changes may be made inthe particular embodiments of the invention disclosed which are withinthe scope and spirit of the invention.

1. A method for using a topology editor to prescribe a device notifiedin response to an event related to the operation of a data network andsaid event comprising the steps of: defining said event pertaining tosaid operation of a data network, wherein said operation concerns thestatus of the data network or a device of said data network; assigningat least one device of said data network to said event by use of saidtopology editor; assigning a rule to said event, wherein said ruledefines at least one condition for triggering a notification of saidevent to said assigned device, and said condition is to be activatedwhen matched to a notification of the operation of said data network. 2.The method of claim 1, wherein said topology editor in view of a SimpleNetwork Management Protocol compatible.
 3. The method of claim 2,wherein the topology editor controls an SNMP manager that transmits SNMPtrap in response to an activated rule.
 4. The method of claim 2, whereinsaid SNMP trap is rendered in accordance
 5. The method of claim 1,wherein an event group is defined for assigning a second device to saidevent by using said topology editor.
 6. The method of claim 5, whereinsaid devices of said event group are notified with an action providerwhen said condition is matched to said notification.
 7. The method ofclaim 6, wherein said notification is rendered in view of a severityoption.
 8. A method for using a topology editor to notify a device inresponse to an event related to the operation of a data networkcomprising the steps of: receiving a notification related to theoperation of the data network, wherein said operation is related to astatus of the data network or a device of the data network; comparingsaid notification to a condition of a rule; notifying said deviceassociated with said event with an action provider, wherein saidassociation with said device and said event was defined by use of saidtopology editor.
 9. The method of claim 8, wherein said topology editorin view of a Simple Network Management Protocol compatible.
 10. Themethod of claim 9, wherein said topology editor controls an SNMP managerthat transmits SNMP trap in response to an activated rule.
 11. Themethod of claim 8, wherein an event group is defined for assigning asecond device to said event by using said topology editor.
 12. Themethod of claim 11, wherein the devices of said event group are notifiedwith the action provider upon the matching of said condition of saidrule to said notification.
 13. The method of claim 8, wherein saidtopology editor operates with in view of a consumer electronics enabledinteroperability standard.
 14. The method of claim 8, wherein saidtopology editor is used to control an action manager for controlling theoperation of said device in view of a second action provider.